-
Notifications
You must be signed in to change notification settings - Fork 421
feat(tracer): auto-disable tracer when for AWS SAM and Chalice environments #3949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(tracer): auto-disable tracer when for AWS SAM and Chalice environments #3949
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #3949 +/- ##
===========================================
- Coverage 96.38% 96.33% -0.05%
===========================================
Files 214 215 +1
Lines 10030 10255 +225
Branches 1846 1913 +67
===========================================
+ Hits 9667 9879 +212
- Misses 259 269 +10
- Partials 104 107 +3 ☔ View full report in Codecov by Sentry. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks very good, but didn't you mention skipping on Amplify too?
Yes, you're right! But I tested locally and didn't see the environment variable, so I'd rather wait, have more time to test and make sure we're not doing anything wrong. I'll open another PR if needed, ok? |
Issue number: #3642
Summary
Changes
This pull request introduces the feature of automatically disable the Tracer when operating within AWS SAM and Chalice environments.
Changes Made
User experience
Before
After
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.